Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3639c8cc2d175924d53a952a40f32a4aa4f385223a8ac28d89d2d81fadba3f08

Tx prefix hash: b30345bebbec125d855a5c9dbf99c9638a340f075256daf30744cc9cda524a63
Tx public key: 1889ad80ca85ea1480a42c9e416e5d506ef9c3d26cc835bc3640ce1c881c0981
Timestamp: 1705159536 Timestamp [UCT]: 2024-01-13 15:25:36 Age [y:d:h:m:s]: 01:101:23:30:11
Block: 934503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334000 RingCT/type: yes/0
Extra: 011889ad80ca85ea1480a42c9e416e5d506ef9c3d26cc835bc3640ce1c881c09810211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1d39b72bf6761fc84e05e562bdb5e68873f2d2f9d593e71f5f2d48d661ace40 0.600000000000 1392517 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": 934513, "vin": [ { "gen": { "height": 934503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1d39b72bf6761fc84e05e562bdb5e68873f2d2f9d593e71f5f2d48d661ace40" } } ], "extra": [ 1, 24, 137, 173, 128, 202, 133, 234, 20, 128, 164, 44, 158, 65, 110, 93, 80, 110, 249, 195, 210, 108, 200, 53, 188, 54, 64, 206, 28, 136, 28, 9, 129, 2, 17, 0, 0, 0, 3, 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