Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f85cf659a6bcf3c3d15950310773751092ef9733040a1a06cfd1632f9c0b3c0

Tx prefix hash: eea1a553fe2ce1b0d3ca38fcfa4a7c0e32a046590f7e2dd40a1c38c218ba356e
Tx public key: 0ff0b73d821154561d739aaad78c95b34dd08c1348bfc54c8a564919244eae1e
Timestamp: 1736976249 Timestamp [UCT]: 2025-01-15 21:24:09 Age [y:d:h:m:s]: 00:152:18:42:25
Block: 1198146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108906 RingCT/type: yes/0
Extra: 010ff0b73d821154561d739aaad78c95b34dd08c1348bfc54c8a564919244eae1e021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67c2b06fa713ffda9bf4f4ea195fa12dd56ee894c76ccfc8f1c8bebad40c99f2 0.600000000000 1684765 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": 1198156, "vin": [ { "gen": { "height": 1198146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67c2b06fa713ffda9bf4f4ea195fa12dd56ee894c76ccfc8f1c8bebad40c99f2" } } ], "extra": [ 1, 15, 240, 183, 61, 130, 17, 84, 86, 29, 115, 154, 170, 215, 140, 149, 179, 77, 208, 140, 19, 72, 191, 197, 76, 138, 86, 73, 25, 36, 78, 174, 30, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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