Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d26af4da66eaee32d3409efb793883dfc53b9a66a6901fbf0523486acef0a1b5

Tx prefix hash: deaabe9be00d57e7a9d6f7e8cf6645fb647ca7eb3ac66fd9cca6231774cc5db4
Tx public key: 74385ec2e9f411927521f0a0d79730749b240a6119dcfd2240e687b99f6fc463
Timestamp: 1706928255 Timestamp [UCT]: 2024-02-03 02:44:15 Age [y:d:h:m:s]: 01:277:18:10:29
Block: 949170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457288 RingCT/type: yes/0
Extra: 0174385ec2e9f411927521f0a0d79730749b240a6119dcfd2240e687b99f6fc46302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 313e4ba08679575614c3dd6f835a4e6427a1a9d5d554adf242eca92bd9e5aa7d 0.600000000000 1407692 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": 949180, "vin": [ { "gen": { "height": 949170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "313e4ba08679575614c3dd6f835a4e6427a1a9d5d554adf242eca92bd9e5aa7d" } } ], "extra": [ 1, 116, 56, 94, 194, 233, 244, 17, 146, 117, 33, 240, 160, 215, 151, 48, 116, 155, 36, 10, 97, 25, 220, 253, 34, 64, 230, 135, 185, 159, 111, 196, 99, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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