Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d713167c74cb9dbc607730fbe76b11e3572ad2978091a612e0e11e4ca1d3e01b

Tx prefix hash: 7071d42bba07ea8f55fc4b527bd7810815b53a9246d56289b7b11b146f23b8b0
Tx public key: 1332fbbee86ae1eca971a9d41b5ddc5f561ed18b67d88075fc2f16e060ce4be4
Timestamp: 1673927881 Timestamp [UCT]: 2023-01-17 03:58:01 Age [y:d:h:m:s]: 02:113:15:38:45
Block: 676455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602910 RingCT/type: yes/0
Extra: 011332fbbee86ae1eca971a9d41b5ddc5f561ed18b67d88075fc2f16e060ce4be40211000000025ec35160000000000000000000

1 output(s) for total of 3.520657056000 dcy

stealth address amount amount idx
00: 45c38b05c227e2bae3fb05a053f189fe8faeacd907bd23c34693a60f4850a33e 3.520657056000 1118172 of 0

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": 676465, "vin": [ { "gen": { "height": 676455 } } ], "vout": [ { "amount": 3520657056, "target": { "key": "45c38b05c227e2bae3fb05a053f189fe8faeacd907bd23c34693a60f4850a33e" } } ], "extra": [ 1, 19, 50, 251, 190, 232, 106, 225, 236, 169, 113, 169, 212, 27, 93, 220, 95, 86, 30, 209, 139, 103, 216, 128, 117, 252, 47, 22, 224, 96, 206, 75, 228, 2, 17, 0, 0, 0, 2, 94, 195, 81, 96, 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