Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b8ca71ef871f50e022959de5e544c1b07d44fe36b147a027a904041a8af534

Tx prefix hash: 9e6820e895c83fa8fe8c33b2d370ba6e5337a9b556e43106deccf0a3c79f01e6
Tx public key: 17db3643c44009abcd0a038fd7ea2ba5542d3fd82d07da246aaac6599761b57f
Timestamp: 1725052171 Timestamp [UCT]: 2024-08-30 21:09:31 Age [y:d:h:m:s]: 01:068:17:27:23
Block: 1099430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307563 RingCT/type: yes/0
Extra: 0117db3643c44009abcd0a038fd7ea2ba5542d3fd82d07da246aaac6599761b57f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71354af5cc35f058a0347fa3af1a11c005cb6c169fd998f866b498322999f502 0.600000000000 1575391 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": 1099440, "vin": [ { "gen": { "height": 1099430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71354af5cc35f058a0347fa3af1a11c005cb6c169fd998f866b498322999f502" } } ], "extra": [ 1, 23, 219, 54, 67, 196, 64, 9, 171, 205, 10, 3, 143, 215, 234, 43, 165, 84, 45, 63, 216, 45, 7, 218, 36, 106, 170, 198, 89, 151, 97, 181, 127, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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