Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff98f438b82009eabb7fc781e838a8ec4e92b7afcd2450c2e11d776c951274b6

Tx prefix hash: ed62deff379a38939e3fc79feb0141a12a6661dc92fca8fe28c846281ce1d6d0
Tx public key: 6eef7eb3d9dd306ed692f4e07bc57b9294ae764949e73d411742128f08ef5a9c
Timestamp: 1733286651 Timestamp [UCT]: 2024-12-04 04:30:51 Age [y:d:h:m:s]: 00:337:16:03:53
Block: 1167605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238844 RingCT/type: yes/0
Extra: 016eef7eb3d9dd306ed692f4e07bc57b9294ae764949e73d411742128f08ef5a9c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ea3ce5e8a38367b46d961008cf7491e69d48de5c8150b7808d5b6b24ee23e9 0.600000000000 1653304 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": 1167615, "vin": [ { "gen": { "height": 1167605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ea3ce5e8a38367b46d961008cf7491e69d48de5c8150b7808d5b6b24ee23e9" } } ], "extra": [ 1, 110, 239, 126, 179, 217, 221, 48, 110, 214, 146, 244, 224, 123, 197, 123, 146, 148, 174, 118, 73, 73, 231, 61, 65, 23, 66, 18, 143, 8, 239, 90, 156, 2, 17, 0, 0, 0, 1, 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