Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b76f19f6c930ad8ca96e3f5e6e727ef4cbf726278adee897907c812f61eeaf3

Tx prefix hash: b669ab1e3355d5335362c14e7ce9dd826a3a8570d75e37c19f372d23bb4d5975
Tx public key: 4d2e2cb4d98bbe9c6c5401bc9a3dbd36f899f3e5739ed9d118674a7d2f7deb61
Timestamp: 1706447989 Timestamp [UCT]: 2024-01-28 13:19:49 Age [y:d:h:m:s]: 01:085:13:56:31
Block: 945172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322262 RingCT/type: yes/0
Extra: 014d2e2cb4d98bbe9c6c5401bc9a3dbd36f899f3e5739ed9d118674a7d2f7deb610211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25a5db93b79b3df7d27a98d3537e267212685573dafd6fb3d69c947607c39cc1 0.600000000000 1403482 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": 945182, "vin": [ { "gen": { "height": 945172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25a5db93b79b3df7d27a98d3537e267212685573dafd6fb3d69c947607c39cc1" } } ], "extra": [ 1, 77, 46, 44, 180, 217, 139, 190, 156, 108, 84, 1, 188, 154, 61, 189, 54, 248, 153, 243, 229, 115, 158, 217, 209, 24, 103, 74, 125, 47, 125, 235, 97, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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