Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f4020eb8ff14b3a6d19b936c0518e4595f4012249e57072d1110b2f33e6de1

Tx prefix hash: 52cb737d87460ba97423ec89170edc6d7cc487af1bf3ee0ecda37aeabc657803
Tx public key: e927c137e7fe9ea99d9c18228eb33ac375b4f1aa8ad50863077038268e999cbb
Timestamp: 1725573573 Timestamp [UCT]: 2024-09-05 21:59:33 Age [y:d:h:m:s]: 00:284:20:55:23
Block: 1103768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203369 RingCT/type: yes/0
Extra: 01e927c137e7fe9ea99d9c18228eb33ac375b4f1aa8ad50863077038268e999cbb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed10f15c09c3bba21ee0c4bbcde24899cb4898170c8b03ae0a8b7e241e41b2a3 0.600000000000 1580725 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": 1103778, "vin": [ { "gen": { "height": 1103768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed10f15c09c3bba21ee0c4bbcde24899cb4898170c8b03ae0a8b7e241e41b2a3" } } ], "extra": [ 1, 233, 39, 193, 55, 231, 254, 158, 169, 157, 156, 24, 34, 142, 179, 58, 195, 117, 180, 241, 170, 138, 213, 8, 99, 7, 112, 56, 38, 142, 153, 156, 187, 2, 17, 0, 0, 0, 2, 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