Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 907314f56b8ce0e4d47b4665bd899bd5390fa412d41b2fe8173bf3926354f778

Tx prefix hash: b219e2c5e0e12ffdaeb237c140298c69b04d4bfc6469fb894f83ba1e0735b376
Tx public key: 3ec74893e924dfcb986c15eaa8599ddcc23f3dcc00a9b15bdff7d2ef110268db
Timestamp: 1698539709 Timestamp [UCT]: 2023-10-29 00:35:09 Age [y:d:h:m:s]: 02:007:21:51:09
Block: 879855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525221 RingCT/type: yes/0
Extra: 013ec74893e924dfcb986c15eaa8599ddcc23f3dcc00a9b15bdff7d2ef110268db021100000002faf35c9c000000000000000000

1 output(s) for total of 0.745890632000 dcy

stealth address amount amount idx
00: d097c22169afdd4859d6f5622506cf30a40f4faec886261c434e20cbf720ada5 0.745890632000 1335395 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": 879865, "vin": [ { "gen": { "height": 879855 } } ], "vout": [ { "amount": 745890632, "target": { "key": "d097c22169afdd4859d6f5622506cf30a40f4faec886261c434e20cbf720ada5" } } ], "extra": [ 1, 62, 199, 72, 147, 233, 36, 223, 203, 152, 108, 21, 234, 168, 89, 157, 220, 194, 63, 61, 204, 0, 169, 177, 91, 223, 247, 210, 239, 17, 2, 104, 219, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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