Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0309442c8b447cf27a5e587387f8bb0a56726e16a0352eb1e6f312df90558b5d

Tx prefix hash: 2d86e64c6a94f3739e24f168fe196a1edf91fe9f9557aedff97fba782515aacb
Tx public key: 355da2c114963eb40375efa9e0258a5af3f96bcef4cb134789a16c24d5b011b9
Timestamp: 1733604943 Timestamp [UCT]: 2024-12-07 20:55:43 Age [y:d:h:m:s]: 00:119:10:55:07
Block: 1170252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85167 RingCT/type: yes/0
Extra: 01355da2c114963eb40375efa9e0258a5af3f96bcef4cb134789a16c24d5b011b90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0929e71db85d92282f282b79f3c00ab89b11f744976c65f40a603c7d1d3abd53 0.600000000000 1655981 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": 1170262, "vin": [ { "gen": { "height": 1170252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0929e71db85d92282f282b79f3c00ab89b11f744976c65f40a603c7d1d3abd53" } } ], "extra": [ 1, 53, 93, 162, 193, 20, 150, 62, 180, 3, 117, 239, 169, 224, 37, 138, 90, 243, 249, 107, 206, 244, 203, 19, 71, 137, 161, 108, 36, 213, 176, 17, 185, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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