Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56c2049c99634a55578641c6efb2ca8a1678b5d337e7841c6b621ee6aeed1d7b

Tx prefix hash: 546453e1283ff1c2a0f476b591e4f4459414873942c25a429e0fdf2d77b4b205
Tx public key: af03f2e070e453f666774982a08b1e101d01c7d6de68d06d352487feceb6c32e
Timestamp: 1718143401 Timestamp [UCT]: 2024-06-11 22:03:21 Age [y:d:h:m:s]: 00:363:03:33:52
Block: 1042166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259572 RingCT/type: yes/0
Extra: 01af03f2e070e453f666774982a08b1e101d01c7d6de68d06d352487feceb6c32e02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b4f8b712ce81bcce910afe9e716ff2ed212de3b5e5ce9b574200ec4f95457f2 0.600000000000 1511017 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": 1042176, "vin": [ { "gen": { "height": 1042166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b4f8b712ce81bcce910afe9e716ff2ed212de3b5e5ce9b574200ec4f95457f2" } } ], "extra": [ 1, 175, 3, 242, 224, 112, 228, 83, 246, 102, 119, 73, 130, 160, 139, 30, 16, 29, 1, 199, 214, 222, 104, 208, 109, 53, 36, 135, 254, 206, 182, 195, 46, 2, 17, 0, 0, 0, 5, 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