Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d7d8d074f3e58d46d72b35724af928b230d1530345692ffb61edfeedcb0b990e

Tx prefix hash: 70d187a4b4559e71f1721668214f42444d5e820fc7235b254d8b8f7c697c8612
Tx public key: 38e06e3a3685f1f892f92ed785d2d16019c2f51fbb0ce04254c9653ddac9785e
Timestamp: 1716391226 Timestamp [UCT]: 2024-05-22 15:20:26 Age [y:d:h:m:s]: 01:011:03:05:25
Block: 1027638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268878 RingCT/type: yes/0
Extra: 0138e06e3a3685f1f892f92ed785d2d16019c2f51fbb0ce04254c9653ddac9785e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7a27cd4eb5222327a88d681b4a03c51fa69c1e5781acb84842bd87fa5c03964 0.600000000000 1495365 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1027648, "vin": [ { "gen": { "height": 1027638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7a27cd4eb5222327a88d681b4a03c51fa69c1e5781acb84842bd87fa5c03964" } } ], "extra": [ 1, 56, 224, 110, 58, 54, 133, 241, 248, 146, 249, 46, 215, 133, 210, 209, 96, 25, 194, 245, 31, 187, 12, 224, 66, 84, 201, 101, 61, 218, 201, 120, 94, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8