Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14cecaa399969e6bf63e407222e6dc5f2514dab71426c88ccf6c91023e9c7a91

Tx prefix hash: d1fdae9254cd9b715bd71d016ecd3efac4b161dd48ebdcd3b58167f1b80c68e3
Tx public key: 07bf4a8ebed442b18c30eff60fb4e773cd6f79ebfb394a7c2d7a088cff754da9
Timestamp: 1731323400 Timestamp [UCT]: 2024-11-11 11:10:00 Age [y:d:h:m:s]: 00:138:21:11:15
Block: 1151341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99075 RingCT/type: yes/0
Extra: 0107bf4a8ebed442b18c30eff60fb4e773cd6f79ebfb394a7c2d7a088cff754da9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b81eb74619866c318ca5d5cc820cdc645af52f9630bf92818159fac59150f3e 0.600000000000 1636854 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": 1151351, "vin": [ { "gen": { "height": 1151341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b81eb74619866c318ca5d5cc820cdc645af52f9630bf92818159fac59150f3e" } } ], "extra": [ 1, 7, 191, 74, 142, 190, 212, 66, 177, 140, 48, 239, 246, 15, 180, 231, 115, 205, 111, 121, 235, 251, 57, 74, 124, 45, 122, 8, 140, 255, 117, 77, 169, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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