Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4116f80106305e9a215257757bdca29cc4071fd215113eb6c159d8a0cae2953e

Tx prefix hash: e49cec16351c380387d01742654d854a0f28f111f6291aecc9dfd25fbd4722d6
Tx public key: e96df2fb8ecf27623d1141bf92d523006b453a0ac3d808edfd0bb6d1257f71dc
Timestamp: 1730784400 Timestamp [UCT]: 2024-11-05 05:26:40 Age [y:d:h:m:s]: 00:132:07:29:54
Block: 1146872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94416 RingCT/type: yes/0
Extra: 01e96df2fb8ecf27623d1141bf92d523006b453a0ac3d808edfd0bb6d1257f71dc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7922ea817f764e7883dc8b5ead1ac75d3475c760f017240e47269e38c540fda 0.600000000000 1631563 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": 1146882, "vin": [ { "gen": { "height": 1146872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7922ea817f764e7883dc8b5ead1ac75d3475c760f017240e47269e38c540fda" } } ], "extra": [ 1, 233, 109, 242, 251, 142, 207, 39, 98, 61, 17, 65, 191, 146, 213, 35, 0, 107, 69, 58, 10, 195, 216, 8, 237, 253, 11, 182, 209, 37, 127, 113, 220, 2, 17, 0, 0, 0, 3, 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