Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c55e4086a7b6e09437c10604bc905d48169df5db0f7a1562673edda9ba5d05d

Tx prefix hash: ea161278e604cfccc4c86cd93377fdac225b407bf1775b7214f235f58889413c
Tx public key: a0d7a15110db27b36d48ff88c39b6f325b6ee9e3de9cfdb2e4b3c6a437bdb8d6
Timestamp: 1706801653 Timestamp [UCT]: 2024-02-01 15:34:13 Age [y:d:h:m:s]: 01:135:11:31:58
Block: 948118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357854 RingCT/type: yes/0
Extra: 01a0d7a15110db27b36d48ff88c39b6f325b6ee9e3de9cfdb2e4b3c6a437bdb8d60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72db59e25b1a71e829c51f2c71d0876617dd634d24887924aa2224636d6b2858 0.600000000000 1406490 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": 948128, "vin": [ { "gen": { "height": 948118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72db59e25b1a71e829c51f2c71d0876617dd634d24887924aa2224636d6b2858" } } ], "extra": [ 1, 160, 215, 161, 81, 16, 219, 39, 179, 109, 72, 255, 136, 195, 155, 111, 50, 91, 110, 233, 227, 222, 156, 253, 178, 228, 179, 198, 164, 55, 189, 184, 214, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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