Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15b71770964b8874e965be687f87a2924d7194430d7562240a23cb279bad6e51

Tx prefix hash: 69c97bc3eb776493f4ee7f9e87c857b3d6e2a6350c90a5d78e05040a9a93a2ad
Tx public key: fa512c75d43803b4f718aaa79ae3b034b5cad8e8d1153095f561bdbb78018d3c
Timestamp: 1574665422 Timestamp [UCT]: 2019-11-25 07:03:42 Age [y:d:h:m:s]: 05:345:21:48:06
Block: 16993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1387563 RingCT/type: yes/0
Extra: 01fa512c75d43803b4f718aaa79ae3b034b5cad8e8d1153095f561bdbb78018d3c021100000004354bbe3b000000000000000000

1 output(s) for total of 539.133127324000 dcy

stealth address amount amount idx
00: e1b0cd6e3e0152fff539271616564a88610d9f448da2e6f833eba3ada4d88e18 539.133127324000 24242 of 0

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": 17003, "vin": [ { "gen": { "height": 16993 } } ], "vout": [ { "amount": 539133127324, "target": { "key": "e1b0cd6e3e0152fff539271616564a88610d9f448da2e6f833eba3ada4d88e18" } } ], "extra": [ 1, 250, 81, 44, 117, 212, 56, 3, 180, 247, 24, 170, 167, 154, 227, 176, 52, 181, 202, 216, 232, 209, 21, 48, 149, 245, 97, 189, 187, 120, 1, 141, 60, 2, 17, 0, 0, 0, 4, 53, 75, 190, 59, 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