Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fec3fdc6831e85dc42d46528975f377ee14db11c331d6f520f1967cb5c7d19d

Tx prefix hash: 4429ab8e3fa95eff1b5be3ee31a1e9a2780972be2667ee94c1a354f860583847
Tx public key: 6b564f94525c6c70fa147ba81aa1803beeafcbc4ad5c0218912b4f9c3c93206d
Timestamp: 1735087009 Timestamp [UCT]: 2024-12-25 00:36:49 Age [y:d:h:m:s]: 00:173:03:43:32
Block: 1182520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123481 RingCT/type: yes/0
Extra: 016b564f94525c6c70fa147ba81aa1803beeafcbc4ad5c0218912b4f9c3c93206d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e658c73f39da96e1e002121bd450e1fb849868f7f6eae9f7e6a2dbd45a5526e 0.600000000000 1668955 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": 1182530, "vin": [ { "gen": { "height": 1182520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e658c73f39da96e1e002121bd450e1fb849868f7f6eae9f7e6a2dbd45a5526e" } } ], "extra": [ 1, 107, 86, 79, 148, 82, 92, 108, 112, 250, 20, 123, 168, 26, 161, 128, 59, 238, 175, 203, 196, 173, 92, 2, 24, 145, 43, 79, 156, 60, 147, 32, 109, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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