Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5725dde4a3f7881116b29c0c0bd7032477e623ff792c7ef93d9c1bfe5c1042bb

Tx prefix hash: c2b2fdeb552e5d893861ba03dceff190aad442104a0ec5bf76f6ffdd287295ba
Tx public key: 1a600dfa53aa830dbfd09cd2c1ea57af3a80f6b49fa62a6f8b8770ad38f8a5df
Timestamp: 1709892601 Timestamp [UCT]: 2024-03-08 10:10:01 Age [y:d:h:m:s]: 01:067:02:26:52
Block: 973774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308976 RingCT/type: yes/0
Extra: 011a600dfa53aa830dbfd09cd2c1ea57af3a80f6b49fa62a6f8b8770ad38f8a5df02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9e26cdb7ada52335ec73adfe28670da456961bbbc2f8861d7be0316f09fa250 0.600000000000 1433713 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": 973784, "vin": [ { "gen": { "height": 973774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9e26cdb7ada52335ec73adfe28670da456961bbbc2f8861d7be0316f09fa250" } } ], "extra": [ 1, 26, 96, 13, 250, 83, 170, 131, 13, 191, 208, 156, 210, 193, 234, 87, 175, 58, 128, 246, 180, 159, 166, 42, 111, 139, 135, 112, 173, 56, 248, 165, 223, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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