Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7df53398c1c3db9f218cad893f77a8a12043d4474c8268d936c91f3cb7bc8dae

Tx prefix hash: 158908b1d9400c985f14c89b450116a787edea8bebf82928f75b88d86b24ef94
Tx public key: bb25e2a8dbc4310166b4d8f3e928d8d25561d85f65db9b04a20cd2780c434372
Timestamp: 1716372683 Timestamp [UCT]: 2024-05-22 10:11:23 Age [y:d:h:m:s]: 00:338:03:05:17
Block: 1027490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241678 RingCT/type: yes/0
Extra: 01bb25e2a8dbc4310166b4d8f3e928d8d25561d85f65db9b04a20cd2780c43437202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1723354aab17c2321a78f0e8c2157abdc5133a1c2b25ec4214a04c0cd87dad 0.600000000000 1495135 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": 1027500, "vin": [ { "gen": { "height": 1027490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1723354aab17c2321a78f0e8c2157abdc5133a1c2b25ec4214a04c0cd87dad" } } ], "extra": [ 1, 187, 37, 226, 168, 219, 196, 49, 1, 102, 180, 216, 243, 233, 40, 216, 210, 85, 97, 216, 95, 101, 219, 155, 4, 162, 12, 210, 120, 12, 67, 67, 114, 2, 17, 0, 0, 0, 3, 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