Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfcf841edf89766c90d7c59588060140af9745fd48e497e35c6fca602864f1d0

Tx prefix hash: bd0e64178040be43bbdd8f1f02b97f460c4354d64aa1f3816e7070951dab64d0
Tx public key: 72ab5798a0aec2c2464cd1dc8c6fdfc5063ff5152f612e997710a1fcc24cee7f
Timestamp: 1742955352 Timestamp [UCT]: 2025-03-26 02:15:52 Age [y:d:h:m:s]: 00:240:15:34:44
Block: 1247367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169738 RingCT/type: yes/0
Extra: 0172ab5798a0aec2c2464cd1dc8c6fdfc5063ff5152f612e997710a1fcc24cee7f021100000003165b77a1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4646be48a92190bb0df8c5e0ba2b6394b1e2f68f2225337b67fea9c4212c0f60 0.600000000000 1734374 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": 1247377, "vin": [ { "gen": { "height": 1247367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4646be48a92190bb0df8c5e0ba2b6394b1e2f68f2225337b67fea9c4212c0f60" } } ], "extra": [ 1, 114, 171, 87, 152, 160, 174, 194, 194, 70, 76, 209, 220, 140, 111, 223, 197, 6, 63, 245, 21, 47, 97, 46, 153, 119, 16, 161, 252, 194, 76, 238, 127, 2, 17, 0, 0, 0, 3, 22, 91, 119, 161, 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