Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52186b53959cd38fa4f9ef3176e61c78bf95e2b8c0afffe4aabe77526bd196f6

Tx prefix hash: 00d93516985e81eb1e8c04aed595d4aa06d0d9d35c5c58a938060f6704adda4b
Tx public key: fa9f3e7ec280b0c7269c025eb3868dce4485cbe8594fc8b68a47c8f4f8678bd4
Timestamp: 1729007509 Timestamp [UCT]: 2024-10-15 15:51:49 Age [y:d:h:m:s]: 00:174:21:52:16
Block: 1132238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124778 RingCT/type: yes/0
Extra: 01fa9f3e7ec280b0c7269c025eb3868dce4485cbe8594fc8b68a47c8f4f8678bd4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35118b806e6a02e28a4a9188a70c8ee6f4483737cf14adde7f41ea2a0a7f1107 0.600000000000 1615151 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": 1132248, "vin": [ { "gen": { "height": 1132238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35118b806e6a02e28a4a9188a70c8ee6f4483737cf14adde7f41ea2a0a7f1107" } } ], "extra": [ 1, 250, 159, 62, 126, 194, 128, 176, 199, 38, 156, 2, 94, 179, 134, 141, 206, 68, 133, 203, 232, 89, 79, 200, 182, 138, 71, 200, 244, 248, 103, 139, 212, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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