Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 689f7836f2f890809e4621126ef3b3d704bcff935aa1e04963e455c7cf521c37

Tx prefix hash: 43f81757b8c8a25830f5802150ced23eadb62fafe7c45f59485b021fc1b44693
Tx public key: 25604820c3c31d85ee555f4ebbd7e030e465e5a0ecfdf06a98ba2d4844cee6f8
Timestamp: 1685352123 Timestamp [UCT]: 2023-05-29 09:22:03 Age [y:d:h:m:s]: 01:276:01:03:57
Block: 770557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458451 RingCT/type: yes/0
Extra: 0125604820c3c31d85ee555f4ebbd7e030e465e5a0ecfdf06a98ba2d4844cee6f802110000000733af99f4000000000000000000

1 output(s) for total of 1.717216128000 dcy

stealth address amount amount idx
00: 44bbddae533a2689d1a4c094d04b8462beea093799b75b463773423de2907e29 1.717216128000 1219868 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": 770567, "vin": [ { "gen": { "height": 770557 } } ], "vout": [ { "amount": 1717216128, "target": { "key": "44bbddae533a2689d1a4c094d04b8462beea093799b75b463773423de2907e29" } } ], "extra": [ 1, 37, 96, 72, 32, 195, 195, 29, 133, 238, 85, 95, 78, 187, 215, 224, 48, 228, 101, 229, 160, 236, 253, 240, 106, 152, 186, 45, 72, 68, 206, 230, 248, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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