Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1bfbb5b797ba459398ab14bcb03c2a5e0876dd4fb4dc10e51ba1d01b152a6f8

Tx prefix hash: d3a5037898a38305a04c38c60b2eacd8bb920341c2a17fd907982bdb358883a6
Tx public key: 386756a48a8e0e0a6d0c1897bdfd6217310ef66a6da70527e82bb8da772cd4af
Timestamp: 1714208155 Timestamp [UCT]: 2024-04-27 08:55:55 Age [y:d:h:m:s]: 01:219:16:23:51
Block: 1009531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415691 RingCT/type: yes/0
Extra: 01386756a48a8e0e0a6d0c1897bdfd6217310ef66a6da70527e82bb8da772cd4af02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fa79a9cde0a5155a6cb4199c7746868fc75ee46dd0a64026fabfa091d4619e1 0.600000000000 1471235 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": 1009541, "vin": [ { "gen": { "height": 1009531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fa79a9cde0a5155a6cb4199c7746868fc75ee46dd0a64026fabfa091d4619e1" } } ], "extra": [ 1, 56, 103, 86, 164, 138, 142, 14, 10, 109, 12, 24, 151, 189, 253, 98, 23, 49, 14, 246, 106, 109, 167, 5, 39, 232, 43, 184, 218, 119, 44, 212, 175, 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