Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca86481a5fcd578461df283072209aeac245158517295e9b4adbbb27521387d

Tx prefix hash: 2e4264834f66657055374e5dcc6f52025f710621f0c1fb826a2590052848fa84
Tx public key: a0fd812dced42915740bbd8c6de5ca5cacc77a7fb2e15689d45450b9f1610b99
Timestamp: 1712594750 Timestamp [UCT]: 2024-04-08 16:45:50 Age [y:d:h:m:s]: 01:272:09:56:43
Block: 996132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453463 RingCT/type: yes/0
Extra: 01a0fd812dced42915740bbd8c6de5ca5cacc77a7fb2e15689d45450b9f1610b9902110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b55a8d1ea91a9f0a3cc268548b136b04b603d6262aebe0b58c623cedeb3bc6a2 0.600000000000 1456548 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": 996142, "vin": [ { "gen": { "height": 996132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b55a8d1ea91a9f0a3cc268548b136b04b603d6262aebe0b58c623cedeb3bc6a2" } } ], "extra": [ 1, 160, 253, 129, 45, 206, 212, 41, 21, 116, 11, 189, 140, 109, 229, 202, 92, 172, 199, 122, 127, 178, 225, 86, 137, 212, 84, 80, 185, 241, 97, 11, 153, 2, 17, 0, 0, 0, 8, 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