Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc2f354d84532217dbcf57381802a0aae9553a135c8227a7cce11417ff407d7f

Tx prefix hash: ac231264c233236fc3f0e7acfad6d3c8db93331d98dd860a53e3c52250b29c58
Tx public key: ce9da6b88872b29860ad5ba40407f0fcdbd521ef3bd717b9f1cfa7dd9776c4d8
Timestamp: 1719663605 Timestamp [UCT]: 2024-06-29 12:20:05 Age [y:d:h:m:s]: 00:337:21:55:41
Block: 1054772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241500 RingCT/type: yes/0
Extra: 01ce9da6b88872b29860ad5ba40407f0fcdbd521ef3bd717b9f1cfa7dd9776c4d802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a401a8ad5b53260852c6e9afb9a11953f9308a06ded7cf2eb84e088564363b65 0.600000000000 1525157 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": 1054782, "vin": [ { "gen": { "height": 1054772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a401a8ad5b53260852c6e9afb9a11953f9308a06ded7cf2eb84e088564363b65" } } ], "extra": [ 1, 206, 157, 166, 184, 136, 114, 178, 152, 96, 173, 91, 164, 4, 7, 240, 252, 219, 213, 33, 239, 59, 215, 23, 185, 241, 207, 167, 221, 151, 118, 196, 216, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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