Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c4396f153d604d690abfd5ecef8fb3c78e272b86c8c57cbd8e498aa2f0b5699

Tx prefix hash: 0a52731a7d2cccb96823c102f6be17e5cfb3fdabb54e3fe1483999c8430e3135
Tx public key: 07bdb750a7a68fa0bc1a19cf15eb886ab997cb21159cf56d240d187e407a0a06
Timestamp: 1718046184 Timestamp [UCT]: 2024-06-10 19:03:04 Age [y:d:h:m:s]: 00:279:17:53:30
Block: 1041357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199931 RingCT/type: yes/0
Extra: 0107bdb750a7a68fa0bc1a19cf15eb886ab997cb21159cf56d240d187e407a0a060211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cde4557c48523f3aea8b37a4e0ad30cf9b4e1643cc5cc0c9aee241bf5a3a65c 0.600000000000 1510022 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": 1041367, "vin": [ { "gen": { "height": 1041357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cde4557c48523f3aea8b37a4e0ad30cf9b4e1643cc5cc0c9aee241bf5a3a65c" } } ], "extra": [ 1, 7, 189, 183, 80, 167, 166, 143, 160, 188, 26, 25, 207, 21, 235, 136, 106, 185, 151, 203, 33, 21, 156, 245, 109, 36, 13, 24, 126, 64, 122, 10, 6, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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