Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1158b8b5554ed1b7e7227d1aa1b0b8b176fab38967c07a9fbd69bfb8ee0d95c6

Tx prefix hash: 6cc611dd639ff0b862b0cc54540b1812aaf2057959d9e8672972a0ff8c38cd76
Tx public key: 61a705a6460ac90d3b0a2f4c26ec4bff0ce3ce702155a126b55b089174885a43
Timestamp: 1706384658 Timestamp [UCT]: 2024-01-27 19:44:18 Age [y:d:h:m:s]: 01:079:23:46:45
Block: 944649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318267 RingCT/type: yes/0
Extra: 0161a705a6460ac90d3b0a2f4c26ec4bff0ce3ce702155a126b55b089174885a4302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0a47fd7b32f083a368cefbcb1e792701b9cc46d3c15faf811d5bb165d141fe 0.600000000000 1402935 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": 944659, "vin": [ { "gen": { "height": 944649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0a47fd7b32f083a368cefbcb1e792701b9cc46d3c15faf811d5bb165d141fe" } } ], "extra": [ 1, 97, 167, 5, 166, 70, 10, 201, 13, 59, 10, 47, 76, 38, 236, 75, 255, 12, 227, 206, 112, 33, 85, 161, 38, 181, 91, 8, 145, 116, 136, 90, 67, 2, 17, 0, 0, 0, 3, 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