Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583bf6532391b62f37f3f5430d5ac142171d6b33ea5376e8f71c23d6aa5ac3f8

Tx prefix hash: 05f4d00e04d569d60a4ee41ab28bad142579d212ef48bc3f40c1e8adf9dc41de
Tx public key: 7ff7b8b8ec31f0e49d4c8afa8e0ba421fa71a76bfe44af54948ace0efef27675
Timestamp: 1733043848 Timestamp [UCT]: 2024-12-01 09:04:08 Age [y:d:h:m:s]: 00:113:14:59:35
Block: 1165606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80985 RingCT/type: yes/0
Extra: 017ff7b8b8ec31f0e49d4c8afa8e0ba421fa71a76bfe44af54948ace0efef27675021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62960381eb735c66361b14f6fc98f0d4af8e84f08e1b407085eafd5a1c0fc8f0 0.600000000000 1651281 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": 1165616, "vin": [ { "gen": { "height": 1165606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62960381eb735c66361b14f6fc98f0d4af8e84f08e1b407085eafd5a1c0fc8f0" } } ], "extra": [ 1, 127, 247, 184, 184, 236, 49, 240, 228, 157, 76, 138, 250, 142, 11, 164, 33, 250, 113, 167, 107, 254, 68, 175, 84, 148, 138, 206, 14, 254, 242, 118, 117, 2, 17, 0, 0, 0, 2, 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