Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35b310849375cd7530218eb048eadfe13b84e63382d1aeda1b24cce4badfd7d9

Tx prefix hash: 10defe19a81c094e315590f4197d378491021c637123e7c5919a930dd20b520b
Tx public key: 7db4a729d40f0a10b2c55ea495cb120b20387de8b709d3975245be41dc0dddd6
Timestamp: 1681227092 Timestamp [UCT]: 2023-04-11 15:31:32 Age [y:d:h:m:s]: 02:007:23:15:58
Block: 736347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527868 RingCT/type: yes/0
Extra: 017db4a729d40f0a10b2c55ea495cb120b20387de8b709d3975245be41dc0dddd6021100000002b3164c24000000000000000000

1 output(s) for total of 2.229403242000 dcy

stealth address amount amount idx
00: b2dbe4400bad18acf8f9101ddc5fb407ac3c161def94d282b4c4a2a21b8f74d7 2.229403242000 1182770 of 0

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": 736357, "vin": [ { "gen": { "height": 736347 } } ], "vout": [ { "amount": 2229403242, "target": { "key": "b2dbe4400bad18acf8f9101ddc5fb407ac3c161def94d282b4c4a2a21b8f74d7" } } ], "extra": [ 1, 125, 180, 167, 41, 212, 15, 10, 16, 178, 197, 94, 164, 149, 203, 18, 11, 32, 56, 125, 232, 183, 9, 211, 151, 82, 69, 190, 65, 220, 13, 221, 214, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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