Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105de5ba00fec1f6808b07362e3c33b4720603ced6fc9bd80c505da91c19a8d9

Tx prefix hash: d5cc8691e4c97b7e1b702f1aedbc4d9c8c18f53b078d53c93fd1b89a60bdc77b
Tx public key: 7a04c442398953cbfbb50e372a0f1ee22cac88ecff45ee4096aafdb766a872c3
Timestamp: 1733558054 Timestamp [UCT]: 2024-12-07 07:54:14 Age [y:d:h:m:s]: 00:105:02:48:54
Block: 1169855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74925 RingCT/type: yes/0
Extra: 017a04c442398953cbfbb50e372a0f1ee22cac88ecff45ee4096aafdb766a872c3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e29539c2472d4a702061050dcf3af3f60afc900425c453c791b8a5c2dfa10a5e 0.600000000000 1655580 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": 1169865, "vin": [ { "gen": { "height": 1169855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e29539c2472d4a702061050dcf3af3f60afc900425c453c791b8a5c2dfa10a5e" } } ], "extra": [ 1, 122, 4, 196, 66, 57, 137, 83, 203, 251, 181, 14, 55, 42, 15, 30, 226, 44, 172, 136, 236, 255, 69, 238, 64, 150, 170, 253, 183, 102, 168, 114, 195, 2, 17, 0, 0, 0, 3, 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