Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a7b897e85f9e3f7f58500dddf4e6ace6955671d8743024ec7e4760c4c99abed

Tx prefix hash: 48e46cb7463a6a7f27755b719d14a1a0dd10a7a22a7e4e18ee1bab046a2afa34
Tx public key: 946e5504e89251808bbdf43c998299bd6d30f5b7013ca0207305c1aa45b17517
Timestamp: 1716391093 Timestamp [UCT]: 2024-05-22 15:18:13 Age [y:d:h:m:s]: 00:231:14:26:10
Block: 1027637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165761 RingCT/type: yes/0
Extra: 01946e5504e89251808bbdf43c998299bd6d30f5b7013ca0207305c1aa45b175170211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10f312d458d451fe1be33c525ffe487db416beb53b7232eaf2f737f0ad45617a 0.600000000000 1495364 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": 1027647, "vin": [ { "gen": { "height": 1027637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f312d458d451fe1be33c525ffe487db416beb53b7232eaf2f737f0ad45617a" } } ], "extra": [ 1, 148, 110, 85, 4, 232, 146, 81, 128, 139, 189, 244, 60, 153, 130, 153, 189, 109, 48, 245, 183, 1, 60, 160, 32, 115, 5, 193, 170, 69, 177, 117, 23, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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