Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 991cdb94553d45856e98649297cf0d9563f9d15d4d6e79c151293223291c85df

Tx prefix hash: efd368b3f68ebae8c0878cc63867b6eda078955b5ea3874c3b19c77cc4f7ba70
Tx public key: 8a43d4eda83d0291e0da0e2ad1983dc3a12bd5d3469d62f18904d7c3ade45a27
Timestamp: 1737008008 Timestamp [UCT]: 2025-01-16 06:13:28 Age [y:d:h:m:s]: 00:154:02:41:06
Block: 1198403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109839 RingCT/type: yes/0
Extra: 018a43d4eda83d0291e0da0e2ad1983dc3a12bd5d3469d62f18904d7c3ade45a27021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b964fcf28e74ca9e95fc20c993e80c683af310494ce3f367fbc4eaec806ab4e5 0.600000000000 1685028 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": 1198413, "vin": [ { "gen": { "height": 1198403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b964fcf28e74ca9e95fc20c993e80c683af310494ce3f367fbc4eaec806ab4e5" } } ], "extra": [ 1, 138, 67, 212, 237, 168, 61, 2, 145, 224, 218, 14, 42, 209, 152, 61, 195, 161, 43, 213, 211, 70, 157, 98, 241, 137, 4, 215, 195, 173, 228, 90, 39, 2, 17, 0, 0, 0, 3, 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