Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4fee10b1a3d6c6f31ef1fa8e20d2872bf7bfb23bb3384e09a9dfd2f2ca2d51f

Tx prefix hash: b833e5781cb3bddf125218aab61e8a978ccd30565a552f5d76cd49d36e3c5da5
Tx public key: 14fa04093bf6411092b630f01599b2f26ad925c6752c399a4affe1e1dc70aca6
Timestamp: 1714340295 Timestamp [UCT]: 2024-04-28 21:38:15 Age [y:d:h:m:s]: 00:356:23:37:59
Block: 1010628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255191 RingCT/type: yes/0
Extra: 0114fa04093bf6411092b630f01599b2f26ad925c6752c399a4affe1e1dc70aca60211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc1d3c3d63a8a74531eb963919ceb4e32724d6feb4c97fe5170c141d941f7f6b 0.600000000000 1472638 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": 1010638, "vin": [ { "gen": { "height": 1010628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc1d3c3d63a8a74531eb963919ceb4e32724d6feb4c97fe5170c141d941f7f6b" } } ], "extra": [ 1, 20, 250, 4, 9, 59, 246, 65, 16, 146, 182, 48, 240, 21, 153, 178, 242, 106, 217, 37, 198, 117, 44, 57, 154, 74, 255, 225, 225, 220, 112, 172, 166, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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