Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f52480b485abcd78670ecddfacba3cc4aba856cfd2b2505f2ee68b8fb5a44146

Tx prefix hash: 3bd5bfea6142a6f96fdc547e1af2c5628221b305ac3cb8d85ce853bf1cb71773
Tx public key: b5aeb5f9872ae5cd17e5a2d78fc1a35404fb7cbaed70e08cef1c21455d6a8551
Timestamp: 1725630950 Timestamp [UCT]: 2024-09-06 13:55:50 Age [y:d:h:m:s]: 01:062:10:11:53
Block: 1104242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303039 RingCT/type: yes/0
Extra: 01b5aeb5f9872ae5cd17e5a2d78fc1a35404fb7cbaed70e08cef1c21455d6a855102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 097aea5e5044024b85432d61aeb7bbbb1e37ef8826e844773ab2de2cfb4b2a5d 0.600000000000 1581321 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": 1104252, "vin": [ { "gen": { "height": 1104242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "097aea5e5044024b85432d61aeb7bbbb1e37ef8826e844773ab2de2cfb4b2a5d" } } ], "extra": [ 1, 181, 174, 181, 249, 135, 42, 229, 205, 23, 229, 162, 215, 143, 193, 163, 84, 4, 251, 124, 186, 237, 112, 224, 140, 239, 28, 33, 69, 93, 106, 133, 81, 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