Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ed1b3cd2e62e8e8f17fc621d8946bff56f2fb8485ad4b13b997da7020f9390

Tx prefix hash: 7e6ec205db9b71240af48680684a451da28af58e8205e607a24d215f6ba4a5e4
Tx public key: f99d2d829f7b96e6380e7cb2f87662457bb0567fa1cd8e11dc8b99ed3bd5435d
Timestamp: 1716017970 Timestamp [UCT]: 2024-05-18 07:39:30 Age [y:d:h:m:s]: 00:321:00:08:49
Block: 1024545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229437 RingCT/type: yes/0
Extra: 01f99d2d829f7b96e6380e7cb2f87662457bb0567fa1cd8e11dc8b99ed3bd5435d02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0ab7dd72d4a0ca81377d26b407be1c47cc2c3e6f6945d5d9c0f36d8aa6e8cae 0.600000000000 1490368 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": 1024555, "vin": [ { "gen": { "height": 1024545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0ab7dd72d4a0ca81377d26b407be1c47cc2c3e6f6945d5d9c0f36d8aa6e8cae" } } ], "extra": [ 1, 249, 157, 45, 130, 159, 123, 150, 230, 56, 14, 124, 178, 248, 118, 98, 69, 123, 176, 86, 127, 161, 205, 142, 17, 220, 139, 153, 237, 59, 213, 67, 93, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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