Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fb26c6785868922520f39bb66c9fa90b47054f7f872b24870a87fcf1ae29b7d

Tx prefix hash: c6d4c0769de1116a3daada73d8df36cb746b9685c1b6824c631b1dea61d53c29
Tx public key: f5c53c68ca38df47bba6233a47db1e236ce56c3c9ac5762f82043748a75b8132
Timestamp: 1745772074 Timestamp [UCT]: 2025-04-27 16:41:14 Age [y:d:h:m:s]: 00:120:03:47:02
Block: 1270707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83653 RingCT/type: yes/0
Extra: 01f5c53c68ca38df47bba6233a47db1e236ce56c3c9ac5762f82043748a75b81320211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78dcb4d377da4bd30ab6e2ef55cf90d2a873163676d69ebdbe287b1a551a032b 0.600000000000 1757952 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": 1270717, "vin": [ { "gen": { "height": 1270707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78dcb4d377da4bd30ab6e2ef55cf90d2a873163676d69ebdbe287b1a551a032b" } } ], "extra": [ 1, 245, 197, 60, 104, 202, 56, 223, 71, 187, 166, 35, 58, 71, 219, 30, 35, 108, 229, 108, 60, 154, 197, 118, 47, 130, 4, 55, 72, 167, 91, 129, 50, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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