Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a8374931c118f9675389f1160d3d6c550bf3b45bb94bef785069f89e8da01aa

Tx prefix hash: 2dce558b1a27c7c56bdd526f87b8eb1a8ef0c108dfa69e9601242e9d15ef6a45
Tx public key: 1747323238c308072fdc4d3604a9d38f77e50c7aaf7dfeda1f4da5118345c1f5
Timestamp: 1722812408 Timestamp [UCT]: 2024-08-04 23:00:08 Age [y:d:h:m:s]: 00:254:22:15:57
Block: 1080873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182091 RingCT/type: yes/0
Extra: 011747323238c308072fdc4d3604a9d38f77e50c7aaf7dfeda1f4da5118345c1f5021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 736eed592d80c28a2e15f36b2435660438d6bfc99204f6e24ea342e4d4703aaf 0.600000000000 1554400 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": 1080883, "vin": [ { "gen": { "height": 1080873 } } ], "vout": [ { "amount": 600000000, "target": { "key": "736eed592d80c28a2e15f36b2435660438d6bfc99204f6e24ea342e4d4703aaf" } } ], "extra": [ 1, 23, 71, 50, 50, 56, 195, 8, 7, 47, 220, 77, 54, 4, 169, 211, 143, 119, 229, 12, 122, 175, 125, 254, 218, 31, 77, 165, 17, 131, 69, 193, 245, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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