Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363734df8f68f8ce69cf5f6957c9d8b28568095e4393a8e58a1e816a1d78b3e9

Tx prefix hash: 84b9eaad91646967ebe64e494d5296d1b0e9bb18612534acc335ced9412275b1
Tx public key: 955110adbc4d7351bb2e2b3753d7697e9db0c8eb820049e0b5b25c0ab1fa19c8
Timestamp: 1713082147 Timestamp [UCT]: 2024-04-14 08:09:07 Age [y:d:h:m:s]: 00:269:17:33:25
Block: 1000187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193090 RingCT/type: yes/0
Extra: 01955110adbc4d7351bb2e2b3753d7697e9db0c8eb820049e0b5b25c0ab1fa19c802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e02a864d9e250c387611f8ed8719e5bd550a3bc3dec933256f79a4388f85791f 0.600000000000 1460683 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": 1000197, "vin": [ { "gen": { "height": 1000187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e02a864d9e250c387611f8ed8719e5bd550a3bc3dec933256f79a4388f85791f" } } ], "extra": [ 1, 149, 81, 16, 173, 188, 77, 115, 81, 187, 46, 43, 55, 83, 215, 105, 126, 157, 176, 200, 235, 130, 0, 73, 224, 181, 178, 92, 10, 177, 250, 25, 200, 2, 17, 0, 0, 0, 5, 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