Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84b0f61ee8c4b1deab1beff7b153e10013f4ebcb76f1a4374445bc4047e72f0c

Tx prefix hash: da3208dfd2618637e9de3a7ca08022a3f830bd8e05049742563fbce304e869a8
Tx public key: 93e5984afc2e3a28fa0b044b4b3d56b20e3f7ac778c8bcc0fae244af4785b727
Timestamp: 1685135129 Timestamp [UCT]: 2023-05-26 21:05:29 Age [y:d:h:m:s]: 02:165:22:19:48
Block: 768765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638374 RingCT/type: yes/0
Extra: 0193e5984afc2e3a28fa0b044b4b3d56b20e3f7ac778c8bcc0fae244af4785b727021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.740855008000 dcy

stealth address amount amount idx
00: 363e2f6626844dc1814257c0b3c74c96423d5a7a891837c49f047fe94b63cae3 1.740855008000 1217976 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": 768775, "vin": [ { "gen": { "height": 768765 } } ], "vout": [ { "amount": 1740855008, "target": { "key": "363e2f6626844dc1814257c0b3c74c96423d5a7a891837c49f047fe94b63cae3" } } ], "extra": [ 1, 147, 229, 152, 74, 252, 46, 58, 40, 250, 11, 4, 75, 75, 61, 86, 178, 14, 63, 122, 199, 120, 200, 188, 192, 250, 226, 68, 175, 71, 133, 183, 39, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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