Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfdf2c42009da07ba7d6ae04251233ed3bf7e31767b2533eb100b97344e988f3

Tx prefix hash: 8e769c8afa031d7a44b1e7dbbfe5090efb92b29aeac6d99bd43a678e6530e1d2
Tx public key: e0390a1484c27cb899356888c66bc1d7b41b5ac997066e9f55fbc59f36137f55
Timestamp: 1718705125 Timestamp [UCT]: 2024-06-18 10:05:25 Age [y:d:h:m:s]: 00:277:14:17:49
Block: 1046829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198356 RingCT/type: yes/0
Extra: 01e0390a1484c27cb899356888c66bc1d7b41b5ac997066e9f55fbc59f36137f5502110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 690c6a222e771b98f5906c8ff339f4316fd8a0f3ef2cc76a63c31a7b2f1ff663 0.600000000000 1516648 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": 1046839, "vin": [ { "gen": { "height": 1046829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "690c6a222e771b98f5906c8ff339f4316fd8a0f3ef2cc76a63c31a7b2f1ff663" } } ], "extra": [ 1, 224, 57, 10, 20, 132, 194, 124, 184, 153, 53, 104, 136, 198, 107, 193, 215, 180, 27, 90, 201, 151, 6, 110, 159, 85, 251, 197, 159, 54, 19, 127, 85, 2, 17, 0, 0, 0, 11, 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