Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e87c9002ed27c7376cd1cdf58a834cefcc2bb0f99d4c2a7252df9f46756ef93

Tx prefix hash: c4843ba1f18f67a2025026a22861c51b46172f2ce163c05010b871ddc23da8d7
Tx public key: 1b00e4e0a9f617bc9db46bfe72bf6bf0b3a0babe89eb242ca203b689ff3964b4
Timestamp: 1710803631 Timestamp [UCT]: 2024-03-18 23:13:51 Age [y:d:h:m:s]: 01:013:05:15:46
Block: 981328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270408 RingCT/type: yes/0
Extra: 011b00e4e0a9f617bc9db46bfe72bf6bf0b3a0babe89eb242ca203b689ff3964b402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2029145b37f6caa4e8fdbc7c509009140c3e65763779aafc8e9617f050014cf7 0.600000000000 1441423 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": 981338, "vin": [ { "gen": { "height": 981328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2029145b37f6caa4e8fdbc7c509009140c3e65763779aafc8e9617f050014cf7" } } ], "extra": [ 1, 27, 0, 228, 224, 169, 246, 23, 188, 157, 180, 107, 254, 114, 191, 107, 240, 179, 160, 186, 190, 137, 235, 36, 44, 162, 3, 182, 137, 255, 57, 100, 180, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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