Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b371c65d91798b4b7747425b3fda67ebd92d20cbc5e08169eecaad9c6717bd67

Tx prefix hash: 410f81c15e4fbd29e9e7b1c6e8278ab762ef9ac117e3701261f53695adcf2746
Tx public key: 34bce107857cae8e23f64d01bb3ca892e5141fff2460b6fd90be8e880a96b9a4
Timestamp: 1714278579 Timestamp [UCT]: 2024-04-28 04:29:39 Age [y:d:h:m:s]: 00:254:23:15:03
Block: 1010121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182497 RingCT/type: yes/0
Extra: 0134bce107857cae8e23f64d01bb3ca892e5141fff2460b6fd90be8e880a96b9a40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9760f27801e352c4115c1e4c6192f70706c1f2428851d713a4f414d2196d2f2 0.600000000000 1471985 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": 1010131, "vin": [ { "gen": { "height": 1010121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9760f27801e352c4115c1e4c6192f70706c1f2428851d713a4f414d2196d2f2" } } ], "extra": [ 1, 52, 188, 225, 7, 133, 124, 174, 142, 35, 246, 77, 1, 187, 60, 168, 146, 229, 20, 31, 255, 36, 96, 182, 253, 144, 190, 142, 136, 10, 150, 185, 164, 2, 17, 0, 0, 0, 5, 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