Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fcb0f1acb079fc61edbedbb83d11485d6267673b0e1223f264da4b1e6132767

Tx prefix hash: 3799504af52d7d4c4d195df2fbe553d1bf8adc512361ab59bc242136a8b640e7
Tx public key: fff0e396fbf6fe7a259f3d578071b1c72978027aad91dfbfd6a5ea38e7e1b421
Timestamp: 1711273843 Timestamp [UCT]: 2024-03-24 09:50:43 Age [y:d:h:m:s]: 01:052:19:17:16
Block: 985229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298705 RingCT/type: yes/0
Extra: 01fff0e396fbf6fe7a259f3d578071b1c72978027aad91dfbfd6a5ea38e7e1b42102110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4259be3085ccc1fa90baba6f5be37061dd51748dcf2516a712389d38697ff91a 0.600000000000 1445438 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": 985239, "vin": [ { "gen": { "height": 985229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4259be3085ccc1fa90baba6f5be37061dd51748dcf2516a712389d38697ff91a" } } ], "extra": [ 1, 255, 240, 227, 150, 251, 246, 254, 122, 37, 159, 61, 87, 128, 113, 177, 199, 41, 120, 2, 122, 173, 145, 223, 191, 214, 165, 234, 56, 231, 225, 180, 33, 2, 17, 0, 0, 0, 16, 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