Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971068435a281bc094e359aaf3ac77abc54322bbf93fe8493fc56bf64b43e97f

Tx prefix hash: 74991139ebd9c5e8d7e8f22d6c0b303564401bfce13bc2b39b8bd7a68748e9eb
Tx public key: b7a19f144df5cc2deaa3835b0e352d6a1a574cfc71281e63319bc8371bfc40ba
Timestamp: 1722924998 Timestamp [UCT]: 2024-08-06 06:16:38 Age [y:d:h:m:s]: 00:169:17:03:14
Block: 1081792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121379 RingCT/type: yes/0
Extra: 01b7a19f144df5cc2deaa3835b0e352d6a1a574cfc71281e63319bc8371bfc40ba021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd7f4f3ad3ecdaa469ec01ab4ce52886f5656f0fdf84fbd330a573572c6ba1b0 0.600000000000 1555613 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": 1081802, "vin": [ { "gen": { "height": 1081792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd7f4f3ad3ecdaa469ec01ab4ce52886f5656f0fdf84fbd330a573572c6ba1b0" } } ], "extra": [ 1, 183, 161, 159, 20, 77, 245, 204, 45, 234, 163, 131, 91, 14, 53, 45, 106, 26, 87, 76, 252, 113, 40, 30, 99, 49, 155, 200, 55, 27, 252, 64, 186, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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