Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d90b07d6eaaa0a09158ed1a04e3e7d3908e69470503649ab4a7654be595d6ca

Tx prefix hash: ef3ca0488631a115abd798bf8deb4baade2002afb2951a2f241e89b8022dfa9f
Tx public key: 506c0053efeb19392af0dfef86bdcdbd1faef2f1ed7b0e00682e8f2ded86e432
Timestamp: 1709482304 Timestamp [UCT]: 2024-03-03 16:11:44 Age [y:d:h:m:s]: 00:356:04:14:21
Block: 970359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254654 RingCT/type: yes/0
Extra: 01506c0053efeb19392af0dfef86bdcdbd1faef2f1ed7b0e00682e8f2ded86e4320211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41b9b974087fb167c3dc30b3a7ee9f56ff422c97922ae313d06d6cc0ef6e88bb 0.600000000000 1430212 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": 970369, "vin": [ { "gen": { "height": 970359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41b9b974087fb167c3dc30b3a7ee9f56ff422c97922ae313d06d6cc0ef6e88bb" } } ], "extra": [ 1, 80, 108, 0, 83, 239, 235, 25, 57, 42, 240, 223, 239, 134, 189, 205, 189, 31, 174, 242, 241, 237, 123, 14, 0, 104, 46, 143, 45, 237, 134, 228, 50, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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