Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6d436ad3ad541c924bed41cc22f866e5499bcbb2eecabab430d38d78a77125

Tx prefix hash: 58a2915967b4e7615d401d7bad41f743aa63c1ec507b1a5322ff941fee916635
Tx public key: ca4fb54becb3b51c92dd599070f26883c7dd4139b487f0dd8d7c30f469651a1d
Timestamp: 1708931774 Timestamp [UCT]: 2024-02-26 07:16:14 Age [y:d:h:m:s]: 00:272:14:10:32
Block: 965798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195156 RingCT/type: yes/0
Extra: 01ca4fb54becb3b51c92dd599070f26883c7dd4139b487f0dd8d7c30f469651a1d02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a3501b4c2ac1b452903ea6ec097ff0c3f8680e0f063c14114bbe3d7fcf8a0a3 0.600000000000 1425553 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": 965808, "vin": [ { "gen": { "height": 965798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a3501b4c2ac1b452903ea6ec097ff0c3f8680e0f063c14114bbe3d7fcf8a0a3" } } ], "extra": [ 1, 202, 79, 181, 75, 236, 179, 181, 28, 146, 221, 89, 144, 112, 242, 104, 131, 199, 221, 65, 57, 180, 135, 240, 221, 141, 124, 48, 244, 105, 101, 26, 29, 2, 17, 0, 0, 0, 4, 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