Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9067a022e09425d72ff424db3a935f141ad12ff856c059c8c4ed7651345d1e5

Tx prefix hash: 98a0ae9dbb284df0566a14a08fc6cda59dce1562cf5450d99e5d5b8aca3f4f6a
Tx public key: 152801079e0a2582208ec6c79251132a1fdba40d397210de217871a8e27d3ebb
Timestamp: 1643493595 Timestamp [UCT]: 2022-01-29 21:59:55 Age [y:d:h:m:s]: 02:330:06:26:30
Block: 428050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 754586 RingCT/type: yes/0
Extra: 01152801079e0a2582208ec6c79251132a1fdba40d397210de217871a8e27d3ebb021100000025d3fcec30000000000000000000

1 output(s) for total of 23.425721128000 dcy

stealth address amount amount idx
00: cda731ae2123e979f3cb6bd2aeecd99a02a8570d2a07d2497e4b84af1990c70e 23.425721128000 837350 of 0

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": 428060, "vin": [ { "gen": { "height": 428050 } } ], "vout": [ { "amount": 23425721128, "target": { "key": "cda731ae2123e979f3cb6bd2aeecd99a02a8570d2a07d2497e4b84af1990c70e" } } ], "extra": [ 1, 21, 40, 1, 7, 158, 10, 37, 130, 32, 142, 198, 199, 146, 81, 19, 42, 31, 219, 164, 13, 57, 114, 16, 222, 33, 120, 113, 168, 226, 125, 62, 187, 2, 17, 0, 0, 0, 37, 211, 252, 236, 48, 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