Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d783413773723ab7d11a4c60eed836e9894bb5bd2a7ab9de81dfd3d877ed9a

Tx prefix hash: 010c05fc21f6303fbb1e6eb59ca6c2b2e3cdbc073444bd0a3482d0a83b8a3e98
Tx public key: ccd013d5501b80534855bb793acee7b66f92d4222de1d41444891befc5d45c52
Timestamp: 1695948542 Timestamp [UCT]: 2023-09-29 00:49:02 Age [y:d:h:m:s]: 01:238:19:10:08
Block: 858357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431762 RingCT/type: yes/0
Extra: 01ccd013d5501b80534855bb793acee7b66f92d4222de1d41444891befc5d45c520211000000034b8f5122000000000000000000

1 output(s) for total of 0.878834267000 dcy

stealth address amount amount idx
00: 7253403bee18d07680bce38b8a9719ee8c8387289b0c2bb37d23ac310b802c92 0.878834267000 1312529 of 0

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": 858367, "vin": [ { "gen": { "height": 858357 } } ], "vout": [ { "amount": 878834267, "target": { "key": "7253403bee18d07680bce38b8a9719ee8c8387289b0c2bb37d23ac310b802c92" } } ], "extra": [ 1, 204, 208, 19, 213, 80, 27, 128, 83, 72, 85, 187, 121, 58, 206, 231, 182, 111, 146, 212, 34, 45, 225, 212, 20, 68, 137, 27, 239, 197, 212, 92, 82, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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