Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df0054ad4e558fa504a0059d7eba27d36d455c2e06ab22fad261e6f54377b66

Tx prefix hash: 113242f6b0d2330137a827ba043314edde8a7d4c35f31665886dd016dff59ab5
Tx public key: d27f87ced537ac0374a08fc9db61eb0bdd9c628eb7d0a73c2368a37ce58e83c3
Timestamp: 1729646721 Timestamp [UCT]: 2024-10-23 01:25:21 Age [y:d:h:m:s]: 00:198:01:26:09
Block: 1137500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141365 RingCT/type: yes/0
Extra: 01d27f87ced537ac0374a08fc9db61eb0bdd9c628eb7d0a73c2368a37ce58e83c3021100000001991650d1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acd803d0fb3cf3b7a4825a6187d7c1eeac5c1e4db1d8a517319b8ccdd2f693ac 0.600000000000 1621003 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": 1137510, "vin": [ { "gen": { "height": 1137500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acd803d0fb3cf3b7a4825a6187d7c1eeac5c1e4db1d8a517319b8ccdd2f693ac" } } ], "extra": [ 1, 210, 127, 135, 206, 213, 55, 172, 3, 116, 160, 143, 201, 219, 97, 235, 11, 221, 156, 98, 142, 183, 208, 167, 60, 35, 104, 163, 124, 229, 142, 131, 195, 2, 17, 0, 0, 0, 1, 153, 22, 80, 209, 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