Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3036733d67c2c6c619ce2174a5a4b6b38a9029327dc940377dbabde408424c7

Tx prefix hash: 85a093e56f29f5c6281b24d7889e63d6b4f1e4002f825f801eb715b9b4e2ec54
Tx public key: 2ffa24fae1af05bfdde944a8dcc481ee32b71d4ce7f3927a42fa469b453b7fa1
Timestamp: 1711644372 Timestamp [UCT]: 2024-03-28 16:46:12 Age [y:d:h:m:s]: 01:009:05:02:51
Block: 988304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267514 RingCT/type: yes/0
Extra: 012ffa24fae1af05bfdde944a8dcc481ee32b71d4ce7f3927a42fa469b453b7fa10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4e7637c57ff7dcbb2c7d6e017ef9ea10811c649e497269dce2b83aaf986582b 0.600000000000 1448579 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": 988314, "vin": [ { "gen": { "height": 988304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4e7637c57ff7dcbb2c7d6e017ef9ea10811c649e497269dce2b83aaf986582b" } } ], "extra": [ 1, 47, 250, 36, 250, 225, 175, 5, 191, 221, 233, 68, 168, 220, 196, 129, 238, 50, 183, 29, 76, 231, 243, 146, 122, 66, 250, 70, 155, 69, 59, 127, 161, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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