Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b44f976cf2bc83a132804f0980cdf6e6f8a24a31bb6a388a7e38fac6b6756cf4

Tx prefix hash: b5870be0484620b43fca0b25964538a05ce51aa18bd9233b1788b540d1900a41
Tx public key: a9cbb1a6e49c86de32bece3d64fc35a4a5c0d9130df9d1b4ba4efbc444d2a5e7
Timestamp: 1725572063 Timestamp [UCT]: 2024-09-05 21:34:23 Age [y:d:h:m:s]: 00:047:07:01:36
Block: 1103755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33841 RingCT/type: yes/0
Extra: 01a9cbb1a6e49c86de32bece3d64fc35a4a5c0d9130df9d1b4ba4efbc444d2a5e702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6197176e052df1d142a4b66a2eb3bdcfe10fb28c7a16babcd755f2bff36f817f 0.600000000000 1580704 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": 1103765, "vin": [ { "gen": { "height": 1103755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6197176e052df1d142a4b66a2eb3bdcfe10fb28c7a16babcd755f2bff36f817f" } } ], "extra": [ 1, 169, 203, 177, 166, 228, 156, 134, 222, 50, 190, 206, 61, 100, 252, 53, 164, 165, 192, 217, 19, 13, 249, 209, 180, 186, 78, 251, 196, 68, 210, 165, 231, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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