Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73bf1a38426aa98b1b4c67938bc5ff1e4c5701a4a7d7ab94d18c3a770953552d

Tx prefix hash: 04ea59cc084f13a17ae202808c48dff2d7402ad7601dc3ac17a87754e0bcfd8e
Tx public key: a7518b0e13d8c9c2172b10df89be28976f56eea0306464a3db408b76273b92c7
Timestamp: 1704467401 Timestamp [UCT]: 2024-01-05 15:10:01 Age [y:d:h:m:s]: 01:083:08:44:20
Block: 928767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320688 RingCT/type: yes/0
Extra: 01a7518b0e13d8c9c2172b10df89be28976f56eea0306464a3db408b76273b92c702110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4711465a045b606c7e257baa9ea9b65ff01bc9000848fdf07f23dc0b35860b44 0.600000000000 1386629 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": 928777, "vin": [ { "gen": { "height": 928767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4711465a045b606c7e257baa9ea9b65ff01bc9000848fdf07f23dc0b35860b44" } } ], "extra": [ 1, 167, 81, 139, 14, 19, 216, 201, 194, 23, 43, 16, 223, 137, 190, 40, 151, 111, 86, 238, 160, 48, 100, 100, 163, 219, 64, 139, 118, 39, 59, 146, 199, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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