Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb297367b3e60082c4693b1a675a6d4160c89b8b3197c30ee4df48d1e85e716f

Tx prefix hash: 566aac64d6454cbc10a99bc331be93b5a7345ed8daa38be4bd8160e55c8f421b
Tx public key: 68a4bdd5d6eac4dbdb7d831372170b8948cf768373c4d42208560c43e9a939e6
Timestamp: 1732186880 Timestamp [UCT]: 2024-11-21 11:01:20 Age [y:d:h:m:s]: 00:135:08:15:19
Block: 1158495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96541 RingCT/type: yes/0
Extra: 0168a4bdd5d6eac4dbdb7d831372170b8948cf768373c4d42208560c43e9a939e6021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 527718254cdf533ded056ed6b7d893830a3497622100b00a61890df637bcb883 0.600000000000 1644124 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": 1158505, "vin": [ { "gen": { "height": 1158495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "527718254cdf533ded056ed6b7d893830a3497622100b00a61890df637bcb883" } } ], "extra": [ 1, 104, 164, 189, 213, 214, 234, 196, 219, 219, 125, 131, 19, 114, 23, 11, 137, 72, 207, 118, 131, 115, 196, 212, 34, 8, 86, 12, 67, 233, 169, 57, 230, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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