Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65046f0023af7a5e1241edd8fcde7f93857352818d44aa4d2c617c13bc3fa0cf

Tx prefix hash: 02bb8bbddf6df38a120d25d4c5076bc0f7f682badacaf5ec363141b25715507c
Tx public key: b4b1812fc2a7cc23a48e0c666b1c85ab4d45af5a808ab7f1e5434f224f6994f6
Timestamp: 1703438726 Timestamp [UCT]: 2023-12-24 17:25:26 Age [y:d:h:m:s]: 01:325:15:27:00
Block: 920256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491584 RingCT/type: yes/0
Extra: 01b4b1812fc2a7cc23a48e0c666b1c85ab4d45af5a808ab7f1e5434f224f6994f602110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 786810ce19004525877770aeacf704a5918ae2dc6b18be9c99193eef7992de5e 0.600000000000 1377934 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": 920266, "vin": [ { "gen": { "height": 920256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "786810ce19004525877770aeacf704a5918ae2dc6b18be9c99193eef7992de5e" } } ], "extra": [ 1, 180, 177, 129, 47, 194, 167, 204, 35, 164, 142, 12, 102, 107, 28, 133, 171, 77, 69, 175, 90, 128, 138, 183, 241, 229, 67, 79, 34, 79, 105, 148, 246, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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