Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0beb1b32acb43acc4d8017527142bf1866dfdbb003d4e36efb48e8f76d8e7d06

Tx prefix hash: d37a2f4f657a0ce444791df559db9e69693655dfdc20973fa379a0a5b7ddeaea
Tx public key: 82d6f3e858f1403f74391438f4271e7aea23b12f592bc43ce641d0d5c1ce69f6
Timestamp: 1703718465 Timestamp [UCT]: 2023-12-27 23:07:45 Age [y:d:h:m:s]: 01:317:22:57:30
Block: 922577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486080 RingCT/type: yes/0
Extra: 0182d6f3e858f1403f74391438f4271e7aea23b12f592bc43ce641d0d5c1ce69f6021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aee28a2160a0834d6280c04e23cfd778cbd1b71a52afee8428e7b649eef0fa1 0.600000000000 1380279 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": 922587, "vin": [ { "gen": { "height": 922577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aee28a2160a0834d6280c04e23cfd778cbd1b71a52afee8428e7b649eef0fa1" } } ], "extra": [ 1, 130, 214, 243, 232, 88, 241, 64, 63, 116, 57, 20, 56, 244, 39, 30, 122, 234, 35, 177, 47, 89, 43, 196, 60, 230, 65, 208, 213, 193, 206, 105, 246, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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