Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6dc9a40870976e4a6ff95c5cb000270dc11a5b42e969d362d83ffdac5b577a

Tx prefix hash: 382f1fdfdbe93ee91d8a3f9584a907e1e429b54af1ab6f12d907b5b891520f11
Tx public key: 8a9b3fd45de862f0784371765817f6edf268bccd91444a29e7a8f0eae8c58461
Timestamp: 1582405547 Timestamp [UCT]: 2020-02-22 21:05:47 Age [y:d:h:m:s]: 04:310:17:34:46
Block: 70426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114637 RingCT/type: yes/0
Extra: 018a9b3fd45de862f0784371765817f6edf268bccd91444a29e7a8f0eae8c5846102111bdf756c00000000000000000000000000

1 output(s) for total of 358.651574058000 dcy

stealth address amount amount idx
00: 3dd34e3d322d3521648c778f6fed17830f598d8f0ef1daa916ba0fe72e71d6c4 358.651574058000 130132 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": 70436, "vin": [ { "gen": { "height": 70426 } } ], "vout": [ { "amount": 358651574058, "target": { "key": "3dd34e3d322d3521648c778f6fed17830f598d8f0ef1daa916ba0fe72e71d6c4" } } ], "extra": [ 1, 138, 155, 63, 212, 93, 232, 98, 240, 120, 67, 113, 118, 88, 23, 246, 237, 242, 104, 188, 205, 145, 68, 74, 41, 231, 168, 240, 234, 232, 197, 132, 97, 2, 17, 27, 223, 117, 108, 0, 0, 0, 0, 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