Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bb74bc5403c3b83194a6531ed3b2a72297fe2b9ff04d22b2ebd6e61d2a0b54c

Tx prefix hash: 0c83aa37904fa5cca91c6dc70bd4eb246d6acf854fda26372cbfb33141bfcece
Tx public key: e98f3c20c2be8192a948b4a02b9687a21921d59babdffca405f2837d900ec5db
Timestamp: 1712903049 Timestamp [UCT]: 2024-04-12 06:24:09 Age [y:d:h:m:s]: 00:264:08:39:11
Block: 998692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189257 RingCT/type: yes/0
Extra: 01e98f3c20c2be8192a948b4a02b9687a21921d59babdffca405f2837d900ec5db02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 482b7c9ee2a20dd944edbd3d53bd2fddf286fff5c3761c5b6b94418a59d55533 0.600000000000 1459144 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": 998702, "vin": [ { "gen": { "height": 998692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "482b7c9ee2a20dd944edbd3d53bd2fddf286fff5c3761c5b6b94418a59d55533" } } ], "extra": [ 1, 233, 143, 60, 32, 194, 190, 129, 146, 169, 72, 180, 160, 43, 150, 135, 162, 25, 33, 213, 155, 171, 223, 252, 164, 5, 242, 131, 125, 144, 14, 197, 219, 2, 17, 0, 0, 0, 2, 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