Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca04a67d7c41e1db08bf85508a4e936bbb860c47676380713e82b400d30e9a90

Tx prefix hash: a8832b1d645351c2d327b864f3696958ca7aa4605fd95582fcc5c114b8d7313a
Tx public key: 8cfef332ccd7b15b7c9faf4e482e63566017b3041d0300f56fb2f218d1b45d74
Timestamp: 1710091313 Timestamp [UCT]: 2024-03-10 17:21:53 Age [y:d:h:m:s]: 01:067:20:28:12
Block: 975420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309507 RingCT/type: yes/0
Extra: 018cfef332ccd7b15b7c9faf4e482e63566017b3041d0300f56fb2f218d1b45d740211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4edde1ee539d29f1108a11ce62bc97db41f55569df2b55ebdcade225996dcc1e 0.600000000000 1435391 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": 975430, "vin": [ { "gen": { "height": 975420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4edde1ee539d29f1108a11ce62bc97db41f55569df2b55ebdcade225996dcc1e" } } ], "extra": [ 1, 140, 254, 243, 50, 204, 215, 177, 91, 124, 159, 175, 78, 72, 46, 99, 86, 96, 23, 179, 4, 29, 3, 0, 245, 111, 178, 242, 24, 209, 180, 93, 116, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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