Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cb4b7f8c7dcc7a67261bd1ec97764abfb1da64611ca07156324830929580377

Tx prefix hash: c2307742dfc9982ea2fb9e7aba24e84369f84d50f606e22085290bf353f03c06
Tx public key: 3b49fd97d47b344c9825c99f4397c21d4aed0b784f897efa2ad69c817c454347
Timestamp: 1702634503 Timestamp [UCT]: 2023-12-15 10:01:43 Age [y:d:h:m:s]: 01:188:01:45:31
Block: 913582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395433 RingCT/type: yes/0
Extra: 013b49fd97d47b344c9825c99f4397c21d4aed0b784f897efa2ad69c817c454347021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf8e2a2aadebf06ecf2de9f415d54fc5388a5cf331d545e27f322cbf1f6bf4e4 0.600000000000 1370856 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": 913592, "vin": [ { "gen": { "height": 913582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf8e2a2aadebf06ecf2de9f415d54fc5388a5cf331d545e27f322cbf1f6bf4e4" } } ], "extra": [ 1, 59, 73, 253, 151, 212, 123, 52, 76, 152, 37, 201, 159, 67, 151, 194, 29, 74, 237, 11, 120, 79, 137, 126, 250, 42, 214, 156, 129, 124, 69, 67, 71, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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