Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea37161c3cd6c04154fa939acf22b339e32b554ad6dd1173feb91f4f3e3fd037

Tx prefix hash: a55a71e9e97ed544cc85583eec906ebdc64d061ce3f5c0a0314ee7cba5d86e44
Tx public key: 10fdcdd7d14fe9b34cd0dbb7e030849eea56f6a3a81878d2999dcd95cdfa1f8d
Timestamp: 1725671595 Timestamp [UCT]: 2024-09-07 01:13:15 Age [y:d:h:m:s]: 01:057:14:58:07
Block: 1104570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299597 RingCT/type: yes/0
Extra: 0110fdcdd7d14fe9b34cd0dbb7e030849eea56f6a3a81878d2999dcd95cdfa1f8d02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e56f7fef2ef960c06d0607cd1fa09348a52d295a4dca25cae60fcc1bee85b4f6 0.600000000000 1581759 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": 1104580, "vin": [ { "gen": { "height": 1104570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e56f7fef2ef960c06d0607cd1fa09348a52d295a4dca25cae60fcc1bee85b4f6" } } ], "extra": [ 1, 16, 253, 205, 215, 209, 79, 233, 179, 76, 208, 219, 183, 224, 48, 132, 158, 234, 86, 246, 163, 168, 24, 120, 210, 153, 157, 205, 149, 205, 250, 31, 141, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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