Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 909e4872d73caafc5ce2849b5fbaa503278f0c7f6b5e1dafaec262c95c05d57a

Tx prefix hash: 6d29da1a18cfb25018acd93b6628f9f3089ac5f67b634a14c6da86bf7ec39ede
Tx public key: aef9e6f8fecf713c121842a46b1cbd29b75984a360e3175a375a9dd182d0193e
Timestamp: 1724750758 Timestamp [UCT]: 2024-08-27 09:25:58 Age [y:d:h:m:s]: 00:259:19:16:42
Block: 1096939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185574 RingCT/type: yes/0
Extra: 01aef9e6f8fecf713c121842a46b1cbd29b75984a360e3175a375a9dd182d0193e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f61329bf19475c37676b865d584fbb9dba63fd3e1bb183fd313433463fe41504 0.600000000000 1572174 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": 1096949, "vin": [ { "gen": { "height": 1096939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f61329bf19475c37676b865d584fbb9dba63fd3e1bb183fd313433463fe41504" } } ], "extra": [ 1, 174, 249, 230, 248, 254, 207, 113, 60, 18, 24, 66, 164, 107, 28, 189, 41, 183, 89, 132, 163, 96, 227, 23, 90, 55, 90, 157, 209, 130, 208, 25, 62, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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