Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b774419b1d71506f8e52dfb5d0041c8b1f96ac7e8f67394eed16dc44b6d4546e

Tx prefix hash: fbf7d7de6ce109afd503ada122abf41653636e57be037d444c5700a53270db2a
Tx public key: ea3e062719281645966f3a93cf4e6526db1d87054e56e9951d2d88f92d664bca
Timestamp: 1720705775 Timestamp [UCT]: 2024-07-11 13:49:35 Age [y:d:h:m:s]: 01:144:11:28:35
Block: 1063412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361809 RingCT/type: yes/0
Extra: 01ea3e062719281645966f3a93cf4e6526db1d87054e56e9951d2d88f92d664bca02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b53082c186fd5e5d62998c7ee5131d23a5e8dcf384cc2d969ebc5f9b2db406f 0.600000000000 1533927 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": 1063422, "vin": [ { "gen": { "height": 1063412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b53082c186fd5e5d62998c7ee5131d23a5e8dcf384cc2d969ebc5f9b2db406f" } } ], "extra": [ 1, 234, 62, 6, 39, 25, 40, 22, 69, 150, 111, 58, 147, 207, 78, 101, 38, 219, 29, 135, 5, 78, 86, 233, 149, 29, 45, 136, 249, 45, 102, 75, 202, 2, 17, 0, 0, 0, 5, 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