Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf93983636382937c2bf757fc64fd060a088b0ce86ef6840e8df821004cbbda5

Tx prefix hash: 788dcaf5d3d91d4db5cfacd9ca46d6d067f64e05a1a6649841077df581859524
Tx public key: d5bbabd83b2d32f2ad7d9400369ef0501cbb5cc9f107e2dd27cfc3405c2bc6ff
Timestamp: 1720025226 Timestamp [UCT]: 2024-07-03 16:47:06 Age [y:d:h:m:s]: 00:276:08:48:13
Block: 1057766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197460 RingCT/type: yes/0
Extra: 01d5bbabd83b2d32f2ad7d9400369ef0501cbb5cc9f107e2dd27cfc3405c2bc6ff02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f44eea89ce878a3d5ddb0c874cbb6f73c25df7a13fb0c9764b38a4147c519d55 0.600000000000 1528207 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": 1057776, "vin": [ { "gen": { "height": 1057766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f44eea89ce878a3d5ddb0c874cbb6f73c25df7a13fb0c9764b38a4147c519d55" } } ], "extra": [ 1, 213, 187, 171, 216, 59, 45, 50, 242, 173, 125, 148, 0, 54, 158, 240, 80, 28, 187, 92, 201, 241, 7, 226, 221, 39, 207, 195, 64, 92, 43, 198, 255, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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