Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba89e386e133d7ac5a9766f93ec322e55b310a065a8324f37eb4ea250344518c

Tx prefix hash: 6a68cc9bb698616f52c393893e32c2167716fb89fe3f5d67589e67ace1709076
Tx public key: a0fd047c3963a1fd78e32d74a9031c4e8c2d8f4fbae5800924bf68a261141f96
Timestamp: 1713452775 Timestamp [UCT]: 2024-04-18 15:06:15 Age [y:d:h:m:s]: 00:253:00:57:40
Block: 1003259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181137 RingCT/type: yes/0
Extra: 01a0fd047c3963a1fd78e32d74a9031c4e8c2d8f4fbae5800924bf68a261141f9602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4118b9de4824f0295f2981d9acb5ba801a7de875fe350f55e8f2f3110a009685 0.600000000000 1463789 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": 1003269, "vin": [ { "gen": { "height": 1003259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4118b9de4824f0295f2981d9acb5ba801a7de875fe350f55e8f2f3110a009685" } } ], "extra": [ 1, 160, 253, 4, 124, 57, 99, 161, 253, 120, 227, 45, 116, 169, 3, 28, 78, 140, 45, 143, 79, 186, 229, 128, 9, 36, 191, 104, 162, 97, 20, 31, 150, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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