Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4d05089b6c3f7b17197877a72c981a664947b709aaec7c2e9d2b9896762dd7

Tx prefix hash: f5542ad0c431ad16fbcf3150f5a041bb031add2ed7b26985e66ad6bf95715229
Tx public key: 80a597cf5f6c6130019fbc532f5eba48c5b2603c418d94eb95c1dec473d859e8
Timestamp: 1736520888 Timestamp [UCT]: 2025-01-10 14:54:48 Age [y:d:h:m:s]: 00:069:01:21:40
Block: 1194377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49154 RingCT/type: yes/0
Extra: 0180a597cf5f6c6130019fbc532f5eba48c5b2603c418d94eb95c1dec473d859e80211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3fdcee0fe75e1bc75c8968a0d762cbf37c22cdcdbc86d4fcfb4b3466c93cf8 0.600000000000 1680946 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": 1194387, "vin": [ { "gen": { "height": 1194377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3fdcee0fe75e1bc75c8968a0d762cbf37c22cdcdbc86d4fcfb4b3466c93cf8" } } ], "extra": [ 1, 128, 165, 151, 207, 95, 108, 97, 48, 1, 159, 188, 83, 47, 94, 186, 72, 197, 178, 96, 60, 65, 141, 148, 235, 149, 193, 222, 196, 115, 216, 89, 232, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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